Hi Michael,
Are you able to figure out why the thread-safety flag would
trigger this ecpg failure with dyntest.pgc ?
Thanks.
Gan
At 3:40 pm +0800 2004/1/5, Liang, Guang Yu (Lucy) wrote:
>Hi, Michael,
>
>When configure without enable-thread-safety, the example
>works perfect. Thank you for the great help!
>
>I still have a few questions:
>1. Is it a known bug or does it only happens in my case?
>2. how will it affect PostgreSQL if we don't use this
> parameter?
>
>Thanks,
>Lucy
>
>-----Original Message-----
>From: Michael Meskes [mailto:meskes@postgresql.org]
>Sent: Tuesday, December 30, 2003 9:12 PM
>To: Liang, Guang Yu (Lucy)
>Cc: 'Michael Meskes'; Seum-Lim Gan; pgsql-bugs@postgresql.org
>Subject: Re: [BUGS] dyntest.pgc not working in 7.4 ?
>
>
>On Mon, Dec 29, 2003 at 03:10:12PM +0800, Liang, Guang Yu (Lucy) wrote:
>> Yes, the enable-thread-safety is used in configure file.
>> Is it expected to be there?
>
>Could you please try to configure without threading? I'd just like to
>remove all components not neccessary to see if the problem still arises.
>
>> I can try an empty database and let you know the result.
>
>ok.
>
>> For machine login, I'm afraid it will be agains Lucent
>> Security policy. Maybe we can try to open a Netmeeting
>> session and share the desktop to see the same window.
>
>Actually I'm afraid that won't be enough, as I can send you all things
>to test via email as well. The problem is that this has such a long
>turnaround. If I could access the machine, or another one with this bug,
>myself, I could test debug the whole stuff.
>
>Michael
>--
>Michael Meskes
>Email: Michael at Fam-Meskes dot De
>ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org
>Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
--
+--------------------------------------------------------+
| Seum-Lim GAN email : slgan@lucent.com |
| Lucent Technologies |
| 2000 N. Naperville Road, 6B-403F tel : (630)-713-6665 |
| Naperville, IL 60566, USA. fax : (630)-713-7272 |
| web : http://inuweb.ih.lucent.com/~slgan |
+--------------------------------------------------------+
